Method, system and apparatus for selective application access and synchronization

ABSTRACT

A method and apparatus for synchronizing data between a mobile communication device and a remote application operating on an external computer. A first application is operable to communicate and synchronize with a remote application operating on an external computer. A second application is operable to communicate and synchronize with the remote application. The mobile communication device receives a user&#39;s identification of a preferred application selected from one of the first and second applications, and uses the preferred application to synchronize the mobile communication device with the remote application.

CROSS-REFERENCE TO RELATED APPLICATIONS

This nonprovisional application is a continuation application claimingthe benefit of the following prior United States patent applicationentitled “METHOD, SYSTEM AND APPARATUS FOR SELECTIVE APPLICATION ACCESSAND SYNCHRONIZATION”, filed Aug. 31, 2005, application Ser. No.11/216,796, the entire contents of which are incorporated herein byreference.

TECHNICAL FIELD OF THE APPLICATION

The present disclosure generally relates to wireless packet data servicenetworks. More particularly, and not by way of any limitation, thepresent disclosure is directed to a mobile communications device andrelated data service network employing a method, apparatus and systemfor selectively synchronizing data between a user preferred applicationand a related remote application.

BACKGROUND

The present disclosure is directed toward synchronizing data between anexternal computer and a mobile communication device. In the field ofmobile communications, it is common for a mobile device and a fixeddevice to employ mirrored databases. Such databases include, but are notlimited to, contacts databases, message databases and calendardatabases. In general, a first database may be stored on a servercontaining a first set of data, and a second database may be stored on amobile communication device containing a second set of data. Eitherdatabase may be completely or partly inclusive of the other database.Where the data stored in one database is expected to mirror the datastored in the other database, it is desirable to update the outdateddatabase expeditiously and efficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the embodiments of the presentdisclosure may be had by reference to the following Detailed Descriptionwhen taken in conjunction with the accompanying drawings wherein:

FIG. 1 depicts an exemplary network environment including a wirelesspacket data service network wherein an embodiment of the presentdisclosure may be practiced;

FIG. 2 depicts a software architectural view of a mobile communicationsdevice operable to selectively synchronize data between a user preferredapplication and a related remote application according to oneembodiment;

FIG. 3 depicts a block diagram of a mobile communications deviceoperable to selectively synchronize data between a user preferredapplication and a related remote application according to oneembodiment;

FIG. 4 depicts a block diagram of a mobile communications systemoperable to selectively synchronize data between a user preferredapplication and a related remote application according to oneembodiment;

FIG. 5 depicts a flow chart showing the process flow for selectivelysynchronizing data between a user preferred application and a relatedremote application according to one embodiment; and

FIG. 6 depicts a message flow diagram showing a message flow selectivelysynchronizing data between a user preferred application and a relatedremote application according to one embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

A system and method of the present disclosure will now be described withreference to various examples of how the embodiments can best be madeand used. Identical reference numerals are used throughout thedescription and several views of the drawings to indicate identical orcorresponding parts, wherein the various elements are not necessarilydrawn to scale.

The present disclosure relates to a device, method and system forselectively synchronizing a preferred application resident on a mobilecommunications device and an application resident on an externalcomputer, which may be a server. According to a first aspect, thepresent disclosure relates to a mobile communication device having afirst application, a second application and a third application residentthereon. The first application is operable to communicate andsynchronize, via a first communication path, with a remote applicationoperating on an external computer. The second application is operable tocommunicate and synchronize with the remote application via a secondcommunication path. The third application is operable to receive a useridentification of a preferred application selected from the first andsecond applications and to restrict a user's access to the otherapplication not selected as the preferred application, thereby using thecommunication path associated with the preferred application tosynchronize the mobile communication device with the external computer.

In certain embodiments, the first application, the second applicationand the remote application may be of the same type. The applicationsmay, for example, be calendar applications, messaging applications or acontacts management applications. The first communication path maycomprise a wireless link, including a cellular link, a WiFi link, aBluetooth link, a Zigbee/IEEE 802.15.4 link or an infrared link, asexamples. The second communication path may comprise a direct wiredconnection between the mobile communication device and the remotecomputer, including a USE connection, an IEEE-1394 connection, anEthernet connection, an RS-232 connection or a PSTN connection, asexamples.

According to a second aspect, the present disclosure relates to methodof synchronizing data between a mobile communication device and anexternal computer. The method comprises the steps of receiving from auser an identification of a preferred application selected from a firstapplication operable to communicate and synchronize via a firstcommunication path with a related remote application executing on theexternal computer and a second application operable to communicate andsynchronize via a second communication path with the related remoteapplication executing on the external computer, storing data associatedwith the preferred application on the mobile communication device,storing data associated with the related remote application on theexternal computer, establishing a connection from the mobilecommunication device to the external computer via the communication pathassociated with the preferred application and synchronizing dataassociated with the preferred application with data associated with therelated remote application via the communication path associated withthe preferred application.

According to a third aspect, the present disclosure relates to a mobilecommunication system. The system comprises a mobile computing devicehaving a first application and a second application stored thereon, anexternal computer having a related remote application executing thereon,means for storing data associated with the first application and secondapplication on the mobile communication device, means for storing dataassociated with the related remote application on the external computer,first means for communicating and synchronizing, via a firstcommunication path, the first application to the related remoteapplication, second means for communicating and synchronizing, via asecond communication path, the second application to the related remoteapplication and means operable to receive a user identification of apreferred application selected from the first application and secondapplication and to restrict user access to the other of the first andsecond applications, thereby using the communication path associatedwith the preferred application to synchronize the mobile communicationdevice with the external computer.

According to fourth aspect, a mobile communication device according tothe present disclosure may comprise a first application operable tocommunicate and synchronize with a remote application operating on anexternal computer. The mobile communication device may further comprisea second application operable to communicate and synchronize with theremote application. The mobile communication device receives a user'sidentification of a preferred application selected from one of the firstand second applications, and uses the preferred application tosynchronize the mobile communication device with the remote application.

In a fifth aspect, the present disclosure may relate to a method ofsynchronizing data between a mobile data communication device and aremote application operating on an external computer. The method maycomprise receiving a user identification of a preferred applicationselected from a first application operable to communicate andsynchronize with the remote application and a second applicationoperable to communicate and synchronize with the remote application;storing data associated with the preferred application on the mobilecommunication device; establishing a connection with the remoteapplication; and sending the data associated with the preferredapplication to the remote application over the established connectionfor synchronization with the remote application.

Referring now to the drawings, and more particularly to FIG. 1, depictedtherein is an exemplary network environment 100 including a wirelesspacket data service network 112 wherein an embodiment of the presentsystem may be practiced. An enterprise network 102, which may be apacket-switched network, can include one or more geographic sites and beorganized as a local area network (LAN), wide area network (WAN) ormetropolitan area network (MAN), et cetera, for serving a plurality ofcorporate users.

A number of application servers 104-1 through 104-N disposed as part ofthe enterprise network 102 are operable to provide or effectuate a hostof internal and external services such as email, video mail, Internetaccess, corporate data access, messaging, calendaring and scheduling,information management, and the like. Accordingly, a diverse array ofpersonal information appliances such as desktop computers, laptopcomputers, palmtop computers, et cetera, although not specifically shownin FIG. 1, may be operably networked to one or more of the applicationservers 104-i, i=1, 2, . . . , N, with respect to the services supportedin the enterprise network 102.

Additionally, a remote services server 106 may be interfaced with theenterprise network 102 for enabling a corporate user to access oreffectuate any of the services from a remote location using a suitablemobile communications device 116. A secure communication link withend-to-end encryption may be established that is mediated through anexternal IP network, i.e., a public packet-switched network such as theInternet 108, as well as the wireless packet data service network 112operable with Mobile communications device 116 via suitable wirelessnetwork infrastructure that includes a base station (BS) 114. In oneembodiment, a trusted relay network 110 may be disposed between theInternet 108 and the infrastructure of wireless packet data servicenetwork 112. By way of example, mobile communications device 116 may bea data-enabled handheld device capable of receiving and sendingmessages, web browsing, interfacing with corporate application servers,et cetera.

For purposes of the present disclosure, the wireless packet data servicenetwork 112 may be implemented in any known or heretofore unknown mobilecommunications technologies and network protocols. For instance, thewireless packet data service network 112 may be comprised of a GeneralPacket Radio Service (GPRS) network that provides a packet radio accessfor mobile devices using the cellular infrastructure of a Global Systemfor Mobile Communications (GSM)-based carrier network. In otherimplementations, the wireless packet data service network 112 maycomprise an Enhanced Data Rates for GSM Evolution (EDGE) network, anIntegrated Digital Enhanced Network (IDEM), a Code Division MultipleAccess (CDMA) network, or any 3rd Generation (3G) network. By way ofproviding an exemplary embodiment, the teachings of the presentdisclosure will be illustrated with a GPRS-based carrier network,although those skilled in the art should readily recognize that thescope of the present disclosure is not limited thereby.

FIG. 2 depicts a software architectural view of a mobile communicationsdevice according to one embodiment. A multi-layer transport stack (TS)206 is operable to provide a generic data transport protocol for anytype of corporate data, including email, via a reliable, secure andseamless continuous connection to a wireless packet data servicenetwork. As illustrated in this embodiment, an integration layer 204A isoperable as an interface between the radio layer 202 and the transportstack 206 of mobile communications device 116. Likewise, anotherintegration layer 204B is provided for interfacing between the transportstack 206 and the user applications 207 supported on the mobilecommunications device 116, e.g., email 208, calendar/scheduler 210,contact management 212 and browser 214. Although not specifically shown,the transport stack 206 may also be interfaced with the operating systemof mobile communications device 116. In another implementation, thetransport stack 206 may be provided as part of a data communicationsclient module operable as a host-independent virtual machine on a mobiledevice. As seen in FIG. 2, an over the air synchronization module 216 isdisposed between radio layer 202 and transport stack 206. Over the airsynchronization module 216 is also operably connected to applicationsblock 207, along with wired synchronization module 218. The function andoperability of over the air synchronization module 216 and wiredsynchronization module 218 are described in detail below.

The bottom layer (Layer 1) of the transport stack 206 is operable as aninterface to the wireless network's packet layer. Layer 1 handles basicservice coordination within the exemplary network environment 100 shownin FIG. 1. For example, when a mobile communications device roams fromone carrier network to another, Layer 1 verifies that the packets arerelayed to the appropriate wireless network and that any packets thatare pending from the previous network are rerouted to the currentnetwork. The top layer (Layer 4) exposes various application interfacesto the services supported on the mobile communications device. Theremaining two layers of the transport stack 206, Layer 2 and Layer 3,are responsible for datagram segmentation/reassembly and security,compression and routing, respectively.

FIG. 3 depicts a block diagram of a mobile communications deviceaccording to one embodiment. It will be recognized by those skilled inthe art upon reference hereto that although an embodiment of mobilecommunications device 116 may comprise an arrangement similar to oneshown in FIG. 3, there can be a number of variations and modifications,in hardware, software or firmware, with respect to the various modulesdepicted. Accordingly, the arrangement of FIG. 3 should be taken asillustrative rather than limiting with respect to the embodiments of thepresent disclosure.

A microprocessor 302 providing for the overall control of an embodimentof Mobile communications device 116 is operably coupled to acommunication subsystem 304 which includes a receiver 308 andtransmitter 314 as well as associated components such as one or morelocal oscillator (LO) modules 310 and a processing module such as adigital signal processor 312. As will be apparent to those skilled inthe field of communications, the particular design of the communicationmodule 304 may be dependent upon the communications network with whichthe mobile communications device 116 is intended to operate.

In one embodiment, the communication module 304 is operable with bothvoice and data communications. Regardless of the particular design,however, signals received by antenna 306 through base station 114 areprovided to receiver 308, which may perform such common receiverfunctions as signal amplification, frequency down conversion, filtering,channel selection, analog-to-digital (A/D) conversion, and the like.Similarly, signals to be transmitted are processed, including modulationand encoding, for example, by digital signal processor 312, and providedto transmitter 314 for digital-to-analog (D/A) conversion, frequency upconversion, filtering, amplification and transmission over the air-radiointerface via antenna 316.

Microprocessor 302 also interfaces with further device subsystems suchas auxiliary input/output (I/O) 318, serial port 320, display 322,keyboard 324, speaker 326, microphone 328, random access memory (RAM)330, a short-range communications subsystem 332, and any other devicesubsystems generally labeled as reference numeral 333. To controlaccess, a Subscriber Identity Module (SIM) or Removable User IdentityModule (RUIM) interface 334 is also provided in communication with themicroprocessor 302.

In one implementation, SIM/RUIM interface 334 is operable with aSIM/RUIM card having a number of key configurations 344 and otherinformation 346 such as identification and subscriber-related data.Operating system software and transport stack software may be embodiedin a persistent storage module (i.e., non-volatile storage) such asFlash memory 335. In one implementation, flash memory 335 may besegregated into different areas, e.g., storage area for computerprograms 336 as well as data storage regions such as device state 337,address book 339, other personal information manager (PIM) data 341, andother data storage areas generally labeled as reference numeral 343. Apair of synchronization modules 216, 218 are operably connected to flashmemory 335, including transport stack 206, as shown. Synchronizationmodules 216, 218 facilitate synchronization of the data stored in mobilecommunication device 116 and external devices. In the embodiment shownin FIG. 3, over the air synchronization module 216 facilitatessynchronization via at least one wireless communication path, whilewired synchronization module 218 facilitates synchronization via atleast one wired communication path.

FIG. 4 depicts a block diagram of a mobile communications systemarchitecture 400 according to one embodiment. Mobile communicationsdevice 116 communicates through base station 114. The network 402through which mobile communications device 116 communicates mayrepresent a combination of other networks, including, as examples,wireless network 112, relay network 110, internet 108 and enterprisenetwork 102 shown in FIG. 1 and described in connection therewith.Network 402 may, of course, have a different architecture, depending onthe particular application.

Mobile communication device 116 incorporates two applications 404, 406having overlapping functionality. In one embodiment, residentapplications 404, 406 are calendar applications. In other embodiments,device resident applications 404, 406 may be messaging or contactsmanagement applications, as examples. Each of device residentapplications 404, 406 stores its data in one of device residentdatabases 408, 410 within flash memory 335. Because there is overlappingfunctionality between device resident application 404 and deviceresident application 406, there is a significant potential for confusionif both of device resident applications 404, 406 are persistentlyavailable to the user. For example, in the embodiment wherein deviceresident applications 404, 406 are calendaring applications, the usercould store an appointment within one of device resident applications404, 406, and then schedule a different appointment in the same timeslot on the other of device resident applications 404, 406. The firstappointment would be stored in device resident database 408 and notdevice resident database 410, while the second appointment would bestored in device resident database 410 and not device resident database408. As a result, the user would have two mutually-inconsistentappointments scheduled for that same time slot. There are a number ofother potentially confusing situations which could result from the useof two calendaring applications having two completely separatedatabases.

In order to prevent the above-described calendaring problem and otherpossible undesirable situations, mobile communication device 116incorporates a user interface module 412 operable to prevent the userfrom having access to both of device resident applications 404, 406during the same period of time. Access to device resident applications404, 406 is controlled according to options selected using an optionsmodule 414. Using options module 414, the user is presented with theoption of using either device resident application 404 or deviceresident application 406, but not both. Once a preferred application isselected from device resident application 404 and device residentapplication 406, the user will not have access to the non-preferredapplication unless and until the user accesses options module 414,deselects the previously preferred application and selects the newlypreferred application. In certain embodiments, identification of a newuser-preferred application may generate an automatic synchronization ofthe database contents between the previously preferred application andthe newly preferred application. In other embodiments, synchronizationmay be at a user's option. In certain embodiments, the non-preferredapplication may be hidden from user access entirely. In alternateembodiments, the non-preferred application may be represented by a“greyed out” icon or menu item. Other representations are familiar tothose of skill in the art of user interface design.

Mobile communication device 116 incorporates over the airsynchronization module 216 and wired synchronization module 218, whichfacilitate data synchronization between mobile communication device 116and application server 104-1. In particular, over the airsynchronization module 216 and wired synchronization module 218facilitate data synchronization between at least one of device residentdatabase 408 and device resident database 410 on the one end, andrelated server database 418 on the other. Each of device residentapplications 404, 406 has access to at least one of over the airsynchronization module 216 and wired synchronization module 218. Incertain embodiments, device resident application 404 or device residentapplication 406 may have at least partial access to more than one ofover the air synchronization module 216 and wired synchronization module218. Over the air synchronization module 216 facilitates datasynchronization through a wireless, or “over the air” communication paththrough antenna 306, base station 114 and network 402, while wiredsynchronization module 218 facilitates data synchronization via a wiredconnection 422.

Application server 104-1 is running related server application 416,which is operable to interface and synchronize with either deviceresident application 404 or device resident application 406 via serversynchronization module 420 and the currently selected one of over theair synchronization module 216 and wired synchronization module 218. Incertain embodiments, the identity of the preferred application and theassociated communication path are transparent to the related serverapplication 416. Accordingly, there is no need to update the relatedserver application 416 to a change in the identity of the preferredapplication. In alternate embodiments, selection of a new user preferredapplication may result in the generation of an update message to relatedserver application 416 informing related server application 416 of theidentity of the newly selected user preferred application. This messagemay also include an identification the communication path through whichfuture synchronization is to take place.

FIG. 5 depicts a flow chart 500 showing one embodiment of a process flowfor synchronization of databases within a mobile communications system.Process flow begins at block 450, where the options module 414 on themobile communication device 116 prompts the user for a preference of oneof at least two resident applications having overlapping functionality.In one embodiment, the user is asked to select between two calendaringapplications. The system then acquires the user's preference (block 452)and stores the preference (block 454). Subsequently, the preferredapplication is presented to the user (block 456). This presentation maybe, for example in the form of an icon displayed on the display of themobile communication device 116. At a certain point in time, the mobilecommunication device 116 opens the preferred application (block 458).

In the embodiment shown in FIG. 5, the mobile communication device 116is operable to synchronize the databases associated with a preferredapplication via a wireless, or “over the air” communication path or viaa wired communication path. In this embodiment, each of the two residentapplications are associated with only one communication path. Inalternate embodiments, one or more of the resident applications may beoperable to synchronize data via multiple communication paths.

In decision block 460, the system determines whether the system iscurrently operable for over the air, or “OTA” synchronization. Thisinquiry relates both to whether there is an available wirelesscommunication path to a server and whether the presently preferredapplication is operable to conduct over the air synchronization.Although this discussion specifically relates to a packet switchedcellular connection, possible wireless communication paths may include,but are not limited to, an IEEE 802.11 (“WiFi”) link, an IEEE 802.15.2(“Bluetooth”) link or an IrDA (infrared) link, as examples. If both ofthe above conditions are TRUE, then process flow continues to block 462,where the application connects to a server via a wireless link, and thento block 470, where the preferred application and a related applicationresident on the server synchronize the database resident on the mobilecommunication device 116 and the related database on the server.

Process flow proceeds from decision block 460 to block 462 only if thesystem is currently operable for over the air synchronization. Thesystem may, however, not currently be operable for over the airsynchronization. This could result, for example, from the unavailabilityof a wireless communication path between the mobile communication device116 and a server. Alternately, the currently preferred application maynot be coded for over the air synchronization.

If for any reason the system is not currently operable for over the airsynchronization, process flow proceeds from block 460 to decision block464. In decision block 464, the system determines whether the system iscurrently operable for wired synchronization. As above, this operabilityrequires that there be an available wired communication path to a serverand that the currently preferred application is coded for wiredsynchronization. Examples of wired communication paths include, but arenot limited to, a Universal Serial Bus (USB) link, a PSTN connection, adigital subscriber line (“DSL”) connection, an EIA323/RS232 link, anIEEE-1394 (“Firewire”) link and an Ethernet link. If a wiredcommunication path is available, process flow proceeds from decisionblock 464 to block 466, where the preferred application connects to theserver via a wired link, and then to block 470, where the systemsynchronizes the two databases.

In certain circumstances, the preferred application may not be able tosynchronize with the server via either a wireless communication path(decision block 460) or a wired communication path (decision block 464).Under such circumstances, process flow proceeds to block 468. Certainembodiments of the system will alert the user as to lack ofsynchronization operability. This alert may take the form of a textalert or an audio alert, as examples.

FIG. 6 depicts a message flow diagram showing the flow of communicationsbetween mobile communications device 116 running two device residentapplications 404, 406 and server 104-1 running a related hostapplication operable to interface and synchronize with each of the twodevice resident applications 404, 406. Initially, device residentapplication 404 is the preferred application. Device residentapplication 404 is operable to communicate and synchronize via awireless communication path. Message flow begins with message 506 fromuser interface 412 to device resident application 404 modifying thecontents of the database related to device resident application 404.Device resident application 404 is operable to alert related serverapplication 416 to the modification, represented by message 508 fromdevice resident application 404 to over the air synchronization module216, which is forwarded as message 510 from over the air synchronizationmodule 216 to base station 114, message 512 from base station 114 tonetwork 402 and message 514 from network 402 to server synchronizationmodule 420. Upon receipt of message 514, synchronization module 420generates message 516 from synchronization module 420 to related serverapplication 416, advising it of the need to update related serverdatabase 418.

After related server database 418 has been updated, related serverapplication 416 generates a confirmation message 518 from related serverapplication 416 to server synchronization module 420, which is thenforwarded as message 520 from server synchronization module 420 tonetwork 402, message 522 from network 402 to base station 114 andmessage 524 from base station 114 to over the air synchronization module216. Over the air synchronization module 216 then forwards thisinformation, as represented by message 526 from over the airsynchronization module 216 to device resident application 404. Deviceresident application 404 then generates message 528 from device residentapplication 404 to user interface 412, thereby informing the user thatthe change has been entered.

Subsequent in time to the above, the user decides to use device residentapplication 406 as the preferred application. Device residentapplication 406 is operable to communicate and synchronize via a wiredcommunication path. Update of the databases begins with message 530 fromuser interface 412 to device resident application 406, alerting deviceresident application 406 of the change. After the change is effectuatedwithin the mobile communication device 116, device resident application406 generates message 532 from device resident application 406 to wiredsynchronization module 218, which is forwarded as message 534 from wiredsynchronization module 218 to server synchronization module 420 and thenmessage 536 from server synchronization module 420 to related serverapplication 416. After updating related server database 418, relatedserver application 416 generates message 542 from related serverapplication 416 to server synchronization module 420. Message 542 isforwarded as message 544 from server synchronization module 420 to wiredsynchronization module 218 and then message 546 from wiredsynchronization module 218 to device resident application 406. Uponreceipt of message 546, device resident application 406 generatesmessage 548 from device resident application 406 to user interface 412,informing the user of the successful update.

It is believed that the operation and construction of the embodiments ofthe present disclosure will be apparent from the Detailed Descriptionset forth above. While the exemplary embodiments shown and described mayhave been characterized as being preferred, it should be readilyunderstood that various changes and modifications could be made thereinwithout departing from the scope of the present disclosure as set forthin the following claims.

1. A mobile communication device comprising: a first applicationoperable to communicate and synchronize with a remote applicationoperating on an external computer; and a second application operable tocommunicate and synchronize with the remote application; wherein themobile communication device receives a user's identification of apreferred application selected from one of the first and secondapplications, and uses the preferred application to synchronize themobile communication device with the remote application.
 2. The mobilecommunication device according to claim 1 wherein the first applicationis operable to communicate with the remote application via a wirelesscommunication link.
 3. The mobile communication device according toclaim 2 wherein the wireless link is selected from a cellular link, aWiFi link, a Bluetooth link, a Zigbee/IEEE 802.15.4 link and an infraredlink.
 4. The mobile communication device according to claim 1 whereinthe second application is operable to communicate with the remoteapplication via a wireless communication link.
 5. The mobilecommunication device according to claim 4 wherein the wireless link isselected from a cellular link, a WiFi link, a Bluetooth link, aZigbee/IEEE 802.15.4 link and an infrared link.
 6. The mobilecommunication device according to claim 1 wherein the first applicationis operable to communicate with the remote application via a wired link.7. The mobile communication device according to claim 1 wherein thesecond application is operable to communicate with the remoteapplication via a wired link.
 8. The mobile communication deviceaccording to claim 1 wherein the external computer is disposed within apacket-switched network comprising a plurality of application servers.9. The mobile communication device according to claim 8 wherein thepacket-switched network is one of a local area network (LAN), awide-area network (WAN), or a metropolitan area network (MAN).
 10. Amethod of synchronizing data between a mobile data communication deviceand a remote application operating on an external computer, the methodcomprising: receiving a user identification of a preferred applicationselected from a first application operable to communicate andsynchronize with the remote application and a second applicationoperable to communicate and synchronize with the remote application;storing data associated with the preferred application on the mobilecommunication device; establishing a connection with the remoteapplication; and sending the data associated with the preferredapplication to the remote application over the established connectionfor synchronization with the remote application.
 11. The methodaccording to claim 10 wherein the established connection with the remoteapplication is a wireless communication link.
 12. The method accordingto claim 11 wherein the wireless communication link is selected from acellular link, a WiFi link, a Bluetooth link, a Zigbee/IEEE 802.15.4link and an infrared link.
 13. The method according to claim 10 whereinthe established connection with the remote application is a wiredconnection.
 14. The method according to claim 13 wherein the wiredconnection comprises one of a USB connection, an IEEE-1394 connection, aPTSN connection, an RS-232 connection, and an Ethernet connection. 15.The method according to claim 10 wherein the external computer isdisposed within a packet-switched network comprising a plurality ofapplication servers.
 16. The method according to claim 15 wherein thepacket-switched network is one of a local area network (LAN), awide-area network (WAN), or metropolitan area network (MAN).